User interface for a portable device including detecting proximity of a finger near a touchscreen to prevent changing the display

ABSTRACT

In a portable electronic device such as a mobile phone with a touchscreen display and a camera, if the camera detects that the user&#39;s finger is near the touchscreen (indicating that the user is about to make a selection) then the display can be prevented from changing while the user&#39;s finger is in proximity to the touchscreen. This can prevent the user from erroneously activating a control such as when the screen display changes suddenly as the user is about to touch an intended currently-displayed control.

CROSS REFERENCES TO RELATED APPLICATIONS

This application claims priority from U.S. Provisional PatentApplication Ser. No. 61/590,284; entitled “USER INTERFACE USING DEVICEAWARENESS”, filed on Jan. 24, 2012, which is hereby incorporated byreference as if set forth in full in this document for all purposes.

BACKGROUND

Many conventional computing devices such as computers, tablets, gameconsoles, televisions, monitors, phones, etc., include a touchscreen. Atouchscreen enables a user to interact directly with displayed objectson the touchscreen by touching the objects with a hand, finger, stylus,or other item. Such displayed objects may include controls that controlfunctions on a phone. Using the touchscreen, the user can activatecontrols by touching corresponding objects on the touchscreen. Forexample, the user can touch an object such as a button on thetouchscreen to activate a voice recognition application on the phone.The user can touch the touchscreen and swipe up and down to scroll apage up and down on the touchscreen.

The touchscreen display is typically controlled by a processor to dim ordarken the screen after a brief period of time since the last touch inorder to save power. For example, 10 seconds after the user has lasttouched the screen the screen may be dimmed or darkened completely. Thedisplay/touchscreen and other functionality of the phone can be turnedoff or put into a “hibernate” or “sleep” mode that uses less power. Ifthe phone goes into a sleep mode, the user can “awaken” or fullyactivate the phone again by, for example, touching a button on thetouchscreen or elsewhere on the device, or by performing a differentaction to reactivate the phone from sleep mode.

The various displayed objects on the touchscreen may be changedfrequently as different application controls, operating system features,or other functions are provided to a user. So, for example, a set ofcontrols may be displayed until the user selects a control. Then a newset of controls or a new page of information may be displayed so thatthe originally-displayed set of controls is no longer visible.

SUMMARY

In one embodiment, the performance of a touchscreen can be improved byusing a camera to check whether a user is about to select a control onthe touchscreen. In a device such as a phone, for example, the cameracan be the typical front-facing camera that faces a user while the useris operating the touch screen. If the camera detects that the user'sfinger is near the touchscreen (indicating that the user is about tomake a selection) then the display can be prevented from changing whilethe user's finger is in proximity to the touchscreen. One embodimentincludes checking if a finger is within a predetermined distance from adisplay screen of a phone before allowing the phone to initiate one ormore predetermined actions. An action by the phone can also be halted ifthe finger is within the predetermined distance. These features canprevent confusion or unintentional operations such as when a user isabout to press a button but the screen changes so that the button is notdisplayed at the time the user's finger actually touches the screen. Insome cases, without these features, the screen may change to place adifferent control at the same spot so that the user may activate anunintended control. Other benefits may be realized.

One embodiment provides checking if a finger is within a predetermineddistance from a display screen of a phone prior to the phone initiatingone or more predetermined actions; and halting an initiation of the oneor more predetermined actions if the finger is within the predetermineddistance.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a diagram of a phone configured to detect a finger ofa user as the finger approaches the display screen of the phone,according to one embodiment.

FIG. 2 illustrates an example simplified flow diagram for enhancingphone functionality based on detection of a finger of a user, accordingto one embodiment.

FIG. 3 illustrates an example user interface, according to oneembodiment.

FIG. 4 illustrates a diagram of a phone next to an ear of a user,according to one embodiment.

FIG. 5 illustrates an example simplified flow diagram for enhancingphone functionality based on detection of a finger of a user, accordingto one embodiment.

FIG. 6 illustrates a diagram of a phone that is held up to the mouth ofa user, where the user is talking into the phone, according to oneembodiment.

FIG. 7 illustrates an example simplified flow diagram for enhancingphone functionality based on detection of a mouth of a user, accordingto one embodiment.

FIG. 8 illustrates a block diagram of a phone, which may be used toimplement the embodiments described herein.

DETAILED DESCRIPTION

Embodiments described herein enhance phone functionality based ondetection of a finger of a user. As described in more detail below inconnection with FIGS. 1, 2, and 3 in some embodiments, a phone checks ifa finger is sufficiently close to the display screen of the phone priorto the phone initiating certain actions, such as activating a sleepmode, dimming the display screen, changing a graphical user interface,control buttons, or content on the display screen, etc. If an actionsuch as going into sleep mode were to occur just before the user touchesthe display screen, the user would need to manually reactivate the phonein order to resume using the phone. A finger that is pointed toward andclose to the display screen is indicative of the user intending toactivate a control on the display screen. Accordingly, if the user'sfinger is close to the display screen, the phone will not performcertain actions. A portion of the user's face may also be detectable inthe background by the camera and this can enable the system to furtherdetermine whether the user is about to try to activate a control.

As described in more detail below in connection with FIGS. 4 and 5, insome embodiments, a phone detects an activation of a control on a phone.The phone checks if a finger is within a predetermined distance from thedisplay screen of the phone prior to the phone initiating the associatedaction (e.g., ending a phone call). If a finger is not within thepredetermined distance from the display screen, it is likely thatanother part of the user such the user's cheek or ear inadvertentlytouched a button on the display screen. A finger that is close to thedisplay screen is indicative of the user intending to activate a controlon the display screen. Accordingly, if the activation of a control doesnot coincide with the presence of the user's finger in front of thedisplay screen, the phone will not perform the action.

Some embodiments described herein enhance phone functionality based ondetection of a mouth of a user. As described in more detail below inconnection with FIGS. 6 and 7, in some embodiments, if a phone detectsboth a voice and mouth, the phone automatically activates a voicerecognition application on a phone. In other words, if a user holds thephone up to the user's mouth and talks, the phone automaticallyinterprets what the user is saying without the user needing to manuallyactivate the voice recognition application.

FIG. 1 illustrates a diagram of a phone 100 configured to detect afinger 102 of a user as finger 102 approaches the display screen 104 ofphone 100, according to one embodiment. In one embodiment, phone 100also includes a camera that has a camera lens 106 configured to detectobjects that are within a predetermined distance from display screen104. In one embodiment, camera lens 106 has a field of view 108 that candetect finger 102 when it is within a close proximity (e.g., 0 to 3inches, or more) to display screen 104.

In one embodiment, camera lens 106 may be a wide angle lens that cancapture an object that is anywhere in front of display screen 104. Inone embodiment, camera lens 106 may be a transparent cover over anexisting camera lens, where camera lens 106 alters the optics to achievea wider field of view and closer focus. As an overlay, camera lens 106may be a film or button placed over an existing lens to alter theoptics. In one embodiment, if camera lens 106 overlays an existingcamera lens, phone 100 corrects any distortions to an image that mayoccur. Camera lens 106 may be permanently fixed to phone 100 ortemporarily fixed to phone 100. In one embodiment, camera lens 106 maybe a permanent auxiliary lens on phone 100, which may be used by anexisting camera or a separate dedicated camera with the purpose ofdetecting a user finger.

While camera lens 106 is shown in the upper center portion of phone 100,camera lens 100 may be located anywhere on the face of phone 100.

In one embodiment, display screen 104 is a touchscreen, which enablesthe user to control phone 100 with finger 102. Note that while a fingeris described in the example embodiments herein, embodiments may beapplied to any object (e.g., stylus, pencil, pen, etc.) that may be usedto operate a touchscreen. For example, phone 100 may detect a stylus,pencil, pen, etc, similarly to phone 100 detecting finger 102.

While camera lens 106 is shown in the upper center portion of phone 100,camera lens 106 may be located anywhere on the face of phone 100.Furthermore, while one lens 106 is shown, phone 100 may use multiplelenses for detection.

FIG. 2 illustrates an example simplified flow diagram for enhancingphone functionality based on detection of a finger of a user, accordingto one embodiment. Referring to both FIGS. 1 and 2, a method isinitiated in block 202, where phone 100 checks if a finger 102 is withina predetermined distance from display screen 104 prior to phone 100initiating one or more predetermined actions. In various embodiments,the predetermined actions may include activating a sleep mode on phone100, dimming display screen 104, changing a graphical user interface ondisplay screen 104, changing control buttons on display screen 104,changing content on display screen 104, etc.

In one embodiment, to check for finger 102, phone 100 takes a pictureprior to phone 100 initiating the one or more predetermined actions.Phone 100 then determines if the picture includes finger 102. In oneembodiment, if the picture includes finger 102, phone 100 then estimatesif finger 102 is within the predetermined distance. In one embodiment,the predetermined distance (e.g., 0 to 3 inches, or more, etc.) is setto a default distance that is set at the factory. In one embodiment, theuser may modify the predetermined distance. The user may also modify thefield of view 108 angle.

In some embodiments, phone 100 may take multiple pictures and determineif a finger is in any of the pictures. In some embodiments, phone 100may take a video and determine if a finger is in the video.

A finger that is close to display screen 104 is indicative of the userintending to activate a control on display screen 104. For example, iffinger 102 is within 2 inches from display screen 104, the user probablyintends to touch display screen 104 to activate a control. If an actionsuch as going into sleep mode were to occur just before the user touchesdisplay screen 104, the user would need to manually reactivate the phoneto in order to resume using the phone.

FIG. 3 illustrates an example user interface 300, according to oneembodiment. As shown, user interface 300 may display a tool bar 302. Insome embodiments, tool bar 302 may include finger indication 304 thatindicates that a finger has been detected. In some embodiments, tool bar302 may also include finger indication 306 that indicates that a buttonhas being selected by an object other than a finger or a pointingdevice. For example, instead of a finger, a user's cheek may beinadvertently touching the display screen. Embodiments directed adisplay screen being touched by an object other than a finger orpointing device are described in more detail below in connection withFIGS. 4 and 5.

In some embodiments, when the user's finger hovers over a control buttonor link (without making actual contact with the display screen), phone100 may initiate a hover function, similar to a mouse hover function.For example, when the user's finger hovers over a control button orlink, phone 100 may display a description of the control button or link.If the user's finger is hovering over a link, phone 100 may display theuniform resource locator (URL) of the link. The phone 100 may displayvarious types of information, depending on the particularimplementation. In various embodiments, phone 100 may determine that theuser's finger is hover when the user's finger is within a predetermineddistance (e.g., within 2 inches) from display screen 104.

In block 204, phone 100 halts an initiation of the one or morepredetermined actions if a finger is within the predetermined distance.In one embodiment, phone 100 deactivates or halts initiation of anyaction until the user initiates an action by touching a control ondisplay screen 104. If finger 102 is not within the predetermineddistance from display screen 104 (e.g., 7 inches, or otherwise notdetectable in the picture), the user probably does not intend to touchdisplay screen 104 to activate a control at that moment. In block 206,if a finger is not within the predetermined distance, phone 100 resumesthe initiation of the one or more predetermined actions.

The following embodiment prevents a scenario where the user presses abutton once to activate a control, but due to a delay in phone 100performing the associated action (e.g., changing pages), the userattempts to repress the same button but inadvertently presses adifferent button on a subsequent page (where both of the buttons happento be located in the same position on display screen 104). In oneembodiment, if phone 100 detects activation of a control button by thetouch of the user, phone 100 takes a picture to detect if a finger ofthe user is within a predetermined distance from display screen 104. Inone embodiment, phone 100 takes the picture if phone 100 determines thatphone 100 will delay performing the action associated with theactivation of the control button more than a predetermined time period(e.g., 0.5 seconds, 1 second, etc.). This predetermined time period maybe set to a default time period at the factory, but may also be reset orchanged by the user. Phone 100 then determines from the picture if afinger is within the predetermined distance. If a finger is determinedto be within the predetermined distance, phone 100 continues with theaction, but halts performing a subsequent action associated withactivation of a button on a subsequent page, where the button on thesubsequent page is located in the same position on display screen 104 asthe pressed button on the previous page. In one embodiment, if a fingeris not determined to be within the predetermined distance, phone 100continues with the action and does not halt performing a subsequentaction associated with activation of a button on a subsequent page.

In one embodiment, the predetermined actions are provided by a defaultlist that is set at the factory. In one embodiment, phone 100 enables auser to select the one or more predetermined actions from apredetermined list of actions. In one embodiment, phone 100 enables auser to override the halting of one or more predetermined actions.

FIG. 4 illustrates a diagram of a phone 400 next to an ear 402 of auser, according to one embodiment. Phone 400 also includes a displayscreen 404 and a camera lens 406 of a camera. In one embodiment, cameralens 406 is configured to detect and recognize an object such as an ear,finger, mouth, stylus, etc., that is within a predetermined distancefrom display screen 404. In one embodiment, camera lens 406 may beconfigured with a field of view 408 that can detect an object when theobject is within a close proximity (e.g., 0 to 3 inches, or more) todisplay screen 404.

In the case where an ear is detected in close proximity to the phone itcan be assumed that the user is trying to listen to the phone. If thephone is currently handling a phone call for the user then it can beassumed that the user is trying to listen to the call. In this case anycontrols on the phone meant to be activated by a finger, stylus, orother object can be disabled. The touch screen on the display can beadvantageously used to increase the volume by detecting that the ear isbeing pressed harder against the touch screen as, for example, where theuser is having difficulty hearing a voice or sound coming from thephone. Other ways to change the volume are possible such as by detectinga swipe in a predetermined direction (up-down, or side-to-side, etc.) sothat the user can change the volume by swiping the phone against theuser's ear.

Other types of “ear” controls are possible and they can vary dependingon the audio application or audio function currently being used. Forexample, if a mobile phone is being used to play radio programs then anear swipe (or swipe or touch by any other part of the body near the earsuch as the head, cheek, etc.) can be used to change the program orchannel. For a music player, a swipe can be used to change the song,album, artist, etc. The ear touch or swipe can be used to hang up thephone or end or mute the audio application. Other functions arepossible.

It is not necessary to actually detect an ear while the user commandsare being given by swiping or touching with an ear. The phone may havedetermined that the user has placed the phone against an ear by notingthat the phone is being raised or manipulated (e.g., with theaccelerometers, compass, or other sensors) and when the camera detectsdarkness or an unrecognizable shape in close proximity (e.g., the user'shead or hair) then it can be assumed that the user is holding the phoneto an ear. It may also be possible that the camera can do an imagerecognition of the side of a head or of a close-up of hair by usingambient light or by using light from the camera's flash orlight-emitting diode (LED) designed to be used for camera images, oreven from the light from the display screen reflecting or illuminatingpart of the head or hair. Other variations are possible.

In one embodiment, camera lens 406 may be a wide angle lens that cancapture an object that is anywhere in front of display screen 404. Inone embodiment, camera lens 406 may be a transparent cover over anexisting camera lens, where camera lens 406 alters the optics to achievea wider field of view and closer focus. As an overlay, camera lens 406may be a film or button placed over an existing lens to alter theoptics. In one embodiment, if camera lens 406 overlays an existingcamera lens, phone 400 corrects any distortions to an image that mayoccur. Camera lens 406 may be permanently fixed to phone 400 ortemporarily fixed to phone 400. In one embodiment, camera lens 406 maybe a permanent auxiliary lens on phone 400, which may be used by anexisting camera or a separate dedicated camera with the purpose ofdetecting a user finger.

While camera lens 406 is shown in the upper center portion of phone 400,camera lens 400 may be located anywhere on the face of phone 400.

In one embodiment, display screen 404 is a touchscreen, which enablesthe user to control phone 400 with a finger, hand, or other body part.For ease of illustration, phone 400 is show next to ear 402 of the useras phone 400 approaches ear 402, and is not yet touching the user'scheek or ear in order to more clearly illustrate portions of phone 400.As described in more detail below, if and when phone 400 makes contactwith the user's cheek or ear, it is possible for the cheek or ear toinadvertently activate a control on display screen 404. Embodimentsdescribed herein address this potential problem.

Note that while a finger is described in the example embodiments herein,embodiments may be applied to any object that may be used to operate atouchscreen. For example, phone 400 may detect a stylus, pencil, pen,etc, similarly to phone 400 detecting a finger.

While camera lens 406 is shown in the upper center portion of phone 400,camera lens 406 may be located anywhere on the face of phone 400.Furthermore, while one lens 406 is shown, phone 400 may use multiplelenses for detection.

FIG. 5 illustrates an example simplified flow diagram for enhancingphone functionality based on detection of a finger of a user, accordingto one embodiment. Referring to both FIGS. 4 and 5, a method isinitiated in block 502, where phone 400 detects an activation of acontrol on phone 400. In block 504, phone 400 checks if a finger iswithin a predetermined distance from display screen 404 prior to phone400 initiating one or more actions associated with the activation. Invarious embodiments, the predetermined actions may include disconnectinga phone call, muting a phone call, putting a phone call on hold,activating a button on a phone keypad, etc. In one embodiment, theactions may include all actions associated with controls on the phone.

In one embodiment, to check for finger 402, phone 400 takes a pictureprior to phone 400 initiating the one or more actions. Phone 400 thendetermines if the picture includes finger 402. In one embodiment, if thepicture includes finger 402, phone 400 then estimates if finger 402 iswithin the predetermined distance. In one embodiment, the predetermineddistance (e.g., 0 to 3 inches, or more, etc.) is set to a defaultdistance that is set at the factory. In one embodiment, the user maymodify the predetermined distance. The user may also modify the field ofview 408 angle.

In some embodiments, phone 400 may take multiple pictures and determineif a finger is in any of the pictures. In some embodiments, phone 400may take a video and determine if a finger is in the video.

A finger that is close to display screen 402 is indicative of the userintending to activate a control on display screen 404. If the user'sfinger 402 is not in front of display screen 404, it is likely thatanother part of the user such the user's cheek or ear inadvertentlytouched a button on display screen 404 and activated a control. The userwould need to then correct such an inadvertent activation of a control.For example, if the user inadvertently ended a call, the user would needto reestablish the call. In one embodiment, phone 400 may determine thata finger 402 is not in front of display screen 404 if the picture issubstantially dark.

As indicated above in connection with FIG. 3, a user interface 300 maydisplay a tool bar 302 that may include finger indication 304 thatindicates that a finger has been detected. The tool bar 302 may alsoinclude finger indication 306 that indicates that a button has beingselected by an object other than a finger or pointing device. In oneembodiment, the display of finger indication 306 may also be anindicator that one or more control icons, or the display screen, isfrozen. In some embodiments, an auditory indication such as a tone orwarning beep may sound in order to indicate that a control button hasbeen selected by an object other than a finger or pointing device. Insome embodiments, the auditory indication may sound in addition to or inlieu of the display of finger indication 306. In some embodiments, inaddition to or in lieu of finger indication 306, tool bar 302 maydisplay an icon or thumbnail photo of an object that has inadvertentlytouched a control button. For example, tool bar 302 may display an iconor thumbnail photo of the user's cheek.

In block 506, phone 400 halts the one or more actions if a finger is notwithin the predetermined distance from display screen 404. In otherwords, if the activation of a control does not coincide with thepresence of the user's finger 402 in front of display screen 404, phone400 will not perform the action. In one embodiment, phone 400 haltsinitiation of any action until the user initiates an action by touchinga control on display screen 404 with the user's finger. In oneembodiment, phone 400 may visually display that one or more buttons arefrozen. For example, in one embodiment, phone 400 may highlight one ormore buttons when frozen. Other visual indications in different formsare possible. For example, in another example embodiment, phone 400 maydisplay a halo over each of one or more buttons when frozen.

If finger 402 is in front of display screen 404, the user probablyintended to touch display screen 404 at that moment and touched thedisplay screen with finger 402 in order to activate a control. In block508, if a finger is within the predetermined distance from displayscreen 404, phone 400 resumes the initiation of the one or morepredetermined actions.

In one embodiment, the predetermined actions are provided by a defaultlist that is set at the factory. In one embodiment, phone 400 enables auser to select the one or more predetermined actions from apredetermined list of actions. In one embodiment, phone 400 enables auser to override the halting of one or more predetermined actions.

In various embodiments, any detection device or sensor may be used tocheck for the finger. For example, such a sensor can be an image sensor,an infrared sensor, etc. In such embodiments, it is not necessary thatphone 400 detects a finger. It is possible for phone 400 to simplydetect an object that is close to display screen 404. In one embodiment,such an object can be a stylus, pencil, pen, etc.

FIG. 6 illustrates a diagram of a phone 600 that is held up to the mouth602 of a user, where the user is talking into phone 600, according toone embodiment. In one embodiment, phone 600 includes a display screen604 and a camera lens 606 of a camera. Camera lens 606 is configured todetect objects (e.g., mouth 602) that are within a predetermineddistance from display screen 604. In one embodiment, camera lens 606 maybe configured with a field of view 608 that can detect mouth 602 when itis within a close proximity (e.g., 3 to 6 inches, or more) to displayscreen 604.

In one embodiment, camera lens 606 may be a wide angle lens that cancapture an object that is anywhere in front of display screen 604. Inone embodiment, camera lens 606 may be a transparent cover over anexisting camera lens, where camera lens 606 alters the optics to achievea wider field of view and closer focus. As an overlay, camera lens 606may be a film or button placed over an existing lens to alter theoptics. In one embodiment, if camera lens 606 overlays an existingcamera lens, phone 600 corrects any distortions to an image that mayoccur. Camera lens 606 may be permanently fixed to phone 600 ortemporarily fixed to phone 600. In one embodiment, camera lens 606 maybe a permanent auxiliary lens on phone 600, which may be used by anexisting camera or a separate dedicated camera with the purpose ofdetecting a user finger.

While camera lens 606 is shown in the upper center portion of phone 600,camera lens 606 may be located anywhere on the face of phone 600.Furthermore, while one lens 606 is shown, phone 600 may use multiplelenses for detection.

FIG. 7 illustrates an example simplified flow diagram for enhancingphone functionality based on detection of a mouth of a user, accordingto one embodiment. Referring to both FIGS. 6 and 7, a method isinitiated in block 702, where phone 600 detects a voice. In oneembodiment, the voice includes speech. In block 704, phone 600 checks ifa mouth 602 is detected. In block 706, phone 600 activates a voicerecognition application on a phone if both the voice and mouth 602 aredetected. In one embodiment, a face is sufficient determine that theuser intends to speak into phone 600. In other words, phone 600activates a voice recognition application on a phone if both the voiceand a face are detected. The voice recognition mode can allow a user toissue a voice command. The phone can assume that if the user's mouth isclose to the phone and the lips are moving and audible speech is beingreceived then the user is talking to or on the phone. If there is noother application currently running so, for example, it is known thatthe user is not on a phone call, making a voice recording, etc. then itcan be assumed that the user is issuing a voice command to the phone.Thus, the phone can be alerted of a voice command simply by the userspeaking toward the phone (either close or one or more feet away) andthe phone can accept the voice command without having the usermanipulate the touch screen or other control to indicate that a voicecommand is being given.

In one embodiment, phone 600 activates a voice recognition applicationon a phone if both the voice and mouth 602 with moving lips aredetected. In one embodiment, if phone 600 detects moving lips, phone 600activates a lip reading application. In one embodiment, phone 600 mayinterpret commands from the user solely by voice recognition, solely bylip reading, or a combination of both voice recognition and lip reading.

In one embodiment, to detect a mouth, phone 600 takes a picture if thevoice is detected. Phone 600 then determines if a mouth is in thepicture. If the mouth is in the picture, phone 600 determines a distancebetween the mouth and the phone. In one embodiment, a mouth isdetermined to be detected if the mouth is within a predetermineddistance from the phone. In some embodiments, phone 600 may takemultiple pictures and determine if a mouth is in any of the pictures. Insome embodiments, phone 600 may take a video and determine if a mouth isin the video.

In one embodiment, the predetermined distance (e.g., 0 to 12 inches, ormore, etc.) is set to a default distance that is set at the factory. Inone embodiment, the user may modify the predetermined distance. The usermay also modify the field of view 608 angle. A face or mouth 602 that isclose to display screen 602 is indicative of the user intending to speakinto phone 600. For example, if the users mouth/face is within 12 inchesfrom display screen 604, the user probably intends to speak into phone600 to activate a control.

In one embodiment, any detection device or sensor may be used to checkfor a mouth. For example, such a sensor can be an image sensor, aproximity sensor, a distance sensor, an accelerometer, an infraredsensor, and an acoustic sensor, etc.

In some embodiments, phone 600 may user mouth detection in combinationwith eye detection. For example, in some embodiments, phone 600 maydetect a mouth that is close to display screen 602 and also detect thatthe users eyes are reading text on the display screen.

FIG. 8 illustrates a block diagram of a phone 800, which may be used toimplement the embodiments described herein, such as phones 100, 400, and600 described herein. In one embodiment, phone 800 may include aprocessor 802 and a memory 804. A phone aware application 806 may bestored on memory 804 or on any other suitable storage location orcomputer-readable medium. In one embodiment, memory 804 may be anon-volatile memory (e.g., random-access memory (RAM), flash memory,etc.). Phone aware application 806 provides instructions that enableprocessor 802 to perform the functions described herein. In oneembodiment, processor 802 may include logic circuitry (not shown).

In one embodiment, phone 800 also includes a detection unit 810. In oneembodiment, detection unit 810 may be a camera that includes an imagesensor 812 and an aperture 814. Image sensor 812 captures images whenimage sensor 812 is exposed to light passing through a camera lens.Aperture 814 regulates light passing through the camera lens. In oneembodiment, after detection unit 810 captures images, detection unit 810may store the images in an image library 816 in memory 804.

In other embodiments, phone 800 may not have all of the componentslisted and/or may have other components instead of, or in addition to,those listed above.

The components of phone 800 shown in FIG. 8 may be implemented by one ormore processors or any combination of hardware devices, as well as anycombination of hardware, software, firmware, etc.

While phone 800 may be described as performing the steps as described inthe embodiments herein, any suitable component or combination ofcomponents of phone 800 may perform the steps described.

Although the description has been described with respect to particularembodiments thereof, these particular embodiments are merelyillustrative, and not restrictive. For example, various embodiments havebeen described herein in the context of a finger being detected.Embodiments described herein may also apply to other objects (e.g.,stylus, pencil, pen, etc.) that a user may use to operate a touchscreen.For example, phone 100 may detect a stylus, pencil, pen, etc, similarlyto phone 100 detecting finger 102. In some embodiments, a user's fingermay be considered a stylus.

Although the description has been described with respect to particularembodiments thereof, these particular embodiments are merelyillustrative, and not restrictive. For example, finger, features maywork with a stylus or other pointing implement Although particularembodiments have been described primarily in association with a phone,it should be apparent that many other types of devices can be thesubject of the various features described herein. In general, any devicethat provides a user interface may benefit from features of theinvention. Although a camera has been used as the primary sensor, otherembodiments can use any detection device or sensor may be used. Forexample, in various embodiments, such a sensor can be an image sensor, aproximity sensor, a distance sensor, an accelerometer, an infraredsensor, an acoustic sensor, etc. In such embodiments, it is notnecessary that a phone detect a finger, a mouth, etc. It is possible forthe phone to simply detect an object that is close to the displayscreen. In one embodiment, such an object may be a part of a hand,stylus, pencil, pen, etc.

Although the description has been described with respect to particularembodiments thereof, these particular embodiments are merelyillustrative, and not restrictive.

Any suitable programming language may be used to implement the routinesof particular embodiments including C, C++, Java, assembly language,etc. Different programming techniques may be employed such as proceduralor object-oriented. The routines may execute on a single processingdevice or on multiple processors. Although the steps, operations, orcomputations may be presented in a specific order, the order may bechanged in particular embodiments. In some particular embodiments,multiple steps shown as sequential in this specification may beperformed at the same time.

Particular embodiments may be implemented in a computer-readable storagemedium (also referred to as a machine-readable storage medium) for useby or in connection with an instruction execution system, apparatus,system, or device. Particular embodiments may be implemented in the formof control logic in software or hardware or a combination of both. Thecontrol logic, when executed by one or more processors, may be operableto perform that which is described in particular embodiments.

A “processor” includes any suitable hardware and/or software system,mechanism or component that processes data, signals or otherinformation. A processor may include a system with a general-purposecentral processing unit, multiple processing units, dedicated circuitryfor achieving functionality, or other systems. Processing need not belimited to a geographic location, or have temporal limitations. Forexample, a processor may perform its functions in “real time,”“offline,” in a “batch mode,” etc. Portions of processing may beperformed at different times and at different locations, by different(or the same) processing systems. A computer may be any processor incommunication with a memory. The memory may be any suitableprocessor-readable storage medium, such as random-access memory (RAM),read-only memory (ROM), magnetic or optical disk, or other tangiblemedia suitable for storing instructions for execution by the processor.

Particular embodiments may be implemented by using a programmed generalpurpose digital computer, by using application specific integratedcircuits, programmable logic devices, field programmable gate arrays,optical, chemical, biological, quantum or nanoengineered systems,components and mechanisms. In general, the functions of particularembodiments may be achieved by any means known in the art. Distributed,networked systems, components, and/or circuits may be used.Communication or transfer of data may be wired, wireless, or by anyother means.

It will also be appreciated that one or more of the elements depicted inthe drawings/figures may also be implemented in a more separated orintegrated manner, or even removed or rendered as inoperable in certaincases, as is useful in accordance with a particular application. It isalso within the spirit and scope to implement a program or code that isstored in a machine-readable medium to permit a computer to perform anyof the methods described above.

As used in the description herein and throughout the claims that follow,“a”, “an”, and “the” include plural references unless the contextclearly dictates otherwise. Also, as used in the description herein andthroughout the claims that follow, the meaning of “in” includes “in” and“on” unless the context clearly dictates otherwise.

While one or more implementations have been described by way of exampleand in terms of the specific embodiments, it is to be understood thatthe implementations are not limited to the disclosed embodiments. To thecontrary, they are intended to cover various modifications and similararrangements as would be apparent to those skilled in the art.Therefore, the scope of the appended claims should be accorded thebroadest interpretation so as to encompass all such modifications andsimilar arrangements.

Thus, while particular embodiments have been described herein, latitudesof modification, various changes, and substitutions are intended in theforegoing disclosures, and it will be appreciated that in some instancessome features of particular embodiments will be employed without acorresponding use of other features without departing from the scope andspirit as set forth. Therefore, many modifications may be made to adapta particular situation or material to the essential scope and spirit.

What is claimed is:
 1. A method comprising: checking if a finger iswithin a predetermined distance from a display screen of a phone priorto the phone initiating one or more predetermined actions, wherein thechecking comprises: taking a picture prior to the phone initiating theone or more predetermined actions; determining if the picture includesthe finger; and if the picture includes the finger, estimating if thefinger is within the predetermined distance; and halting an initiationof the one or more predetermined actions if the finger is within thepredetermined distance.
 2. The method of claim 1, wherein the one ormore predetermined actions comprise activating a sleep mode on thephone.
 3. The method of claim 1, wherein the one or more predeterminedactions comprise dimming the display screen.
 4. The method of claim 1,wherein the one or more predetermined actions comprise changing agraphical user interface on the display screen.
 5. The method of claim1, wherein the one or more predetermined actions comprise changingcontrol buttons on the display screen.
 6. The method of claim 1, whereinthe one or more predetermined actions comprise changing content on thedisplay screen.
 7. The method of claim 1, further comprising resumingthe initiation of the one or more predetermined actions if the finger isnot within the predetermined distance.
 8. The method of claim 1, furthercomprising enabling a user to select the one or more actions from apredetermined list of actions.
 9. The method of claim 1, furthercomprising enabling a user to override the halting of one or moreactions.
 10. The method of claim 1, wherein the finger is a stylus. 11.An apparatus comprising: one or more processors; and logic encoded inone or more tangible media for execution by the one or more processors,and when executed operable to: check if a finger is within apredetermined distance from a display screen of a phone prior to thephone initiating one or more predetermined actions, wherein the logicwhen executed is further operable to: take a picture prior to the phoneinitiating the one or more predetermined actions; determine if thepicture includes the finger; and if the picture includes the finger,estimate if the finger is within the predetermined distance; and halt aninitiation of the one or more predetermined actions if the finger iswithin the predetermined distance.
 12. The apparatus of claim 11,further comprising a sensor that checks for the finger.
 13. Theapparatus of claim 11, further comprising a sensor that checks for thefinger, wherein the sensor is one or more of an image sensor, aproximity sensor, a distance sensor, an accelerometer, an infraredsensor, and an acoustic sensor.
 14. The apparatus of claim 11, furthercomprising a camera that has a lens configured to detect objects withinthe predetermined distance from the display screen.
 15. The apparatus ofclaim 11, wherein the one or more predetermined actions compriseactivating a sleep mode on the phone.
 16. A computer-readable storagemedium carrying one or more sequences of instructions thereon, theinstructions when executed by a processor cause the processor to: checkif a finger is within a predetermined distance from a display screen ofa phone prior to the phone initiating one or more predetermined actions,wherein the instructions further cause the processor to: take a pictureprior to the phone initiating the one or more predetermined actions;determine if the picture includes the finger; and if the pictureincludes the finger, estimate if the finger is within the predetermineddistance; and halt an initiation of the one or more predeterminedactions if the finger is within the predetermined distance.